Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: Fix submit workflow #35

Merged
merged 2 commits into from
Oct 19, 2024
Merged

ci: Fix submit workflow #35

merged 2 commits into from
Oct 19, 2024

Conversation

Semro
Copy link
Contributor

@Semro Semro commented Oct 16, 2024

Hi! I was using your workflow as an example and ran into some issues.

  1. Include hidden files, because .output listed in .gitignore
  2. gh command didn't work for me.
    1. Not really sure why we should run changelogen again if we have CHANGELOG.md, just pass it to gh command.
    2. We can specify token in env.
    3. Include assets

@@ -55,6 +55,7 @@ jobs:
with:
path: .output/*.zip
if-no-files-found: error
include-hidden-files: true
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah yeah, haven't used this since this action started ignoring hidden files. Thanks!

Comment on lines 91 to 94
run: pnpx changelogen@latest gh release ${{ steps.version.outputs.newVersion }} --token ${{ github.token }}
run: gh release create v${{ steps.version.outputs.newVersion }} .output/*.zip -F CHANGELOG.md
env:
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

changelogen gh release just syncs the changelog with the latest release, it doesn't regenerate the changelog or anything like that. So these are doing almost the same thing.

The -F CHANGELOG.md is using your entire changelog as your release notes... Which I don't think you want?

I don't know why github.token worked for me and not for you, weird. You can replace it with secrets.GITHUB_TOKEN like you did, that's fine.

And uploading the zip files as artifacts would be a good idea...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, I was confused with changelogen gh release command, not realizing it's a subcommand of changelogen package. So, it might be working correctly.

Copy link
Owner

@aklinker1 aklinker1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I reverted the changelogen step, and added a seperate one for uploading ZIPs to release.

@aklinker1 aklinker1 merged commit ed5a04d into aklinker1:main Oct 19, 2024
1 check failed
@Semro Semro deleted the patch-1 branch October 19, 2024 07:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants